[pgAdmin][RM4993] [Accessibility] Read-only controls and disabled controls needs to be separately identified

From: Aditya Toshniwal <aditya(dot)toshniwal(at)enterprisedb(dot)com>
To: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: [pgAdmin][RM4993] [Accessibility] Read-only controls and disabled controls needs to be separately identified
Date: 2020-01-22 12:15:53
Message-ID: CAM9w-_n8hzWzjP33g-KFy-BpBk-t6_u26U7M8atkHD8z4+3nyw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

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"

Attachment Content-Type Size
RM4993.patch application/octet-stream 81.2 KB

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Akshay Joshi 2020-01-22 12:57:45 [pgAdmin][RM2554] declarative partitioning - support for multi-level partition
Previous Message Nick Barnes 2020-01-21 13:25:06 Error when editing char(n)[] cells