| From: | Akshay Joshi <akshay(dot)joshi(at)enterprisedb(dot)com> |
|---|---|
| To: | Aditya Toshniwal <aditya(dot)toshniwal(at)enterprisedb(dot)com> |
| Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: [pgAdmin][RM4993] [Accessibility] Read-only controls and disabled controls needs to be separately identified |
| Date: | 2020-01-23 07:36:13 |
| Message-ID: | CANxoLDe4kzgQffGA6p_PdVoOFnBM2wjr9nuXFFzP4pt5_7601w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
Hi Aditya
On Wed, Jan 22, 2020 at 5:46 PM Aditya Toshniwal <
aditya(dot)toshniwal(at)enterprisedb(dot)com> wrote:
> Hi Hackers,
>
> Attached is the patch to allow input controls to be set as readonly
> instead of disabled.
> I've also changed the code for the nodes to make sure properties tab have
> readonly fields wherever applicable. This will allow tab navigation in
> properties tab and also allow screen readers to read it.
> Please note that, I've not visited each and every node create/edit dialog
> to identify what should be readonly or what should be disabled as it
> depends on business logic. The patch is mainly for the properties tab.
>
> Kindly review.
>
> --
> Thanks and Regards,
> Aditya Toshniwal
> pgAdmin Hacker | Sr. Software Engineer | EnterpriseDB India | Pune
> "Don't Complain about Heat, Plant a TREE"
>
--
*Thanks & Regards*
*Akshay Joshi*
*Sr. Software Architect*
*EnterpriseDB Software India Private Limited*
*Mobile: +91 976-788-8246*
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Akshay Joshi | 2020-01-23 07:38:01 | Re: [pgAdmin][RM4993] [Accessibility] Read-only controls and disabled controls needs to be separately identified |
| Previous Message | Akshay Joshi | 2020-01-23 07:09:05 | Re: [pgAdmin4][RM#5107] Add tab navigation for tabs under explain panel in query tool |