Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lN8QF-0005sm-GA for pgadmin-hackers@arkaria.postgresql.org; Fri, 19 Mar 2021 06:15:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lN8QE-0004y0-EN for pgadmin-hackers@arkaria.postgresql.org; Fri, 19 Mar 2021 06:15:46 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lN8QE-0004xt-2k for pgadmin-hackers@lists.postgresql.org; Fri, 19 Mar 2021 06:15:46 +0000 Received: from mail-il1-x134.google.com ([2607:f8b0:4864:20::134]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lN8Q6-0000Yz-EF for pgadmin-hackers@postgresql.org; Fri, 19 Mar 2021 06:15:45 +0000 Received: by mail-il1-x134.google.com with SMTP id t18so7071723iln.3 for ; Thu, 18 Mar 2021 23:15:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=tOLRx6mWEa2rrW9y0kJefjGYwG93KwLkmzBMZkiG9zY=; b=Zxye8AVHt+d4PL3VQ92C1VWi9WdZ6U88XMaUoR7QM+rtiB0xBynpuvfhoOtlh7crFO WLVsIZXfFhgzhdsoOltv/TuKjKOeZomTgaZptr1MXvRVT2xl1z2uVr/TD9CRZoLsk0hs jtt8IkjWMfwaFqbk7LaSryt2ApKaxBXFCgyftj2r6R1Z81e9SX7SgM8y2cJbrvY1fQ0V URXQaebqINiUfbDzLdCjPK9Z5o0YzgyW/w4hyOzVTJGUdUQaycxU/Jt+CVnwKgAC1Ms7 ScpOBvRPvJ6j8ZC2rIywR/FBIDqitVdupGFxnN3qx3HSQQx4QH733DFSZZ59QgVkrquE gAig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=tOLRx6mWEa2rrW9y0kJefjGYwG93KwLkmzBMZkiG9zY=; b=LJmrQzMRCvfIulHhh3fCYzE7PYSXILiDbfYzZGsXMAAtJPEwHAFZj9wS0OlQ7EnFnk oh3pM55wp5hjZ8VcxqZd6f2hLGnY1c8MipeoGprq5XnDe1vLAEnc1EA6FLuwkj/DH49d cPTjGRQGYfJ0JD54FmFnxQkdrdeEFkI/fn9uncbdW3m7BbNewtiKugZf3DJ8bIV4Crzr UoScprd/8f+RgSqKO92g96E+HdtOQAcagrejENSBk4+BEUsV9pMAiLq5yXoORPpVus5n 9EqhWGm5nuC2JmbL3uVpraUQ/kN9USCmyBqtuowpzCfyAKqmp9rECIBpFtOe3UEsnaFm pwYw== X-Gm-Message-State: AOAM532uUfKAcUqlKHVIJjPI0s8cAdKKEUph7LGuxGil+BDJgicrAcbx ltUdBmifVulsj69Ie1Fh4sSNUM3s/nt2MLa6N3FGrHrnfmlqZryO3P0O1tnnfXKckzU2+FCEWuF 1Ja07C8WtLUeXDOXq8VU+IYKnJH7WYl3js6b5brrmA1mufwuXVjgh+Mu4fBYLKCmo6GqgcyuZRy MqALYtqejL93Nb7nCnvbXz7dUnpJ71JANsmMzI63sX7jmRJWWk/3faanrciQ== X-Google-Smtp-Source: ABdhPJzNDIuEyt7ZNbHBqbLt7uF7gObBWGRfPmtZQSs6A2/ygMl44ePPst6ai1slVWyzt+PoFsoPVwN5v9DuVyaWawM= X-Received: by 2002:a92:db0f:: with SMTP id b15mr1001074iln.236.1616134536119; Thu, 18 Mar 2021 23:15:36 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Akshay Joshi Date: Fri, 19 Mar 2021 11:45:25 +0530 Message-ID: Subject: Re: [pgAdmin4][Patch]: RM 6317 - Toggle buttons are inaccessible To: Khushboo Vashi Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary="000000000000ef621a05bddda45e" X-CLOUD-SEC-AV-Info: enterprisedb,google_mail,monitor X-CLOUD-SEC-AV-Sent: true X-Gm-Spam: 0 X-Gm-Phishy: 0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000ef621a05bddda45e Content-Type: text/plain; charset="UTF-8" Thanks, patch applied. On Wed, Mar 17, 2021 at 2:36 PM Khushboo Vashi < khushboo.vashi@enterprisedb.com> wrote: > Hi, > > Please find the attached patch to fix the RM #6317: Toggle buttons are > inaccessible. > > Our toggle buttons are not the HTML buttons but the combinations of HTML > tags which function as a toggle button. As the toggle button itself doesn't > have a label/title as it wrapped around a div, we have provided the extra > hidden label above the toggle button div, so on receiving the focus, toggle > button will read the label we provided(For example: "Can login?, Yes, > Toggle. Button''), which was working as expected with Chrome Screen Reader > extension, on which we have tested. Unfortunately, most screen readers like > VoiceOver, NVDA etc.. read the label and the button as different tags, so > when the label gets the focus, the screen reader reads it as "Can login? > Yes, Toggle Button", and when we try to click it, we can't, as it is just a > label. > > To fix this issue, I have put the label inside the toggle div, so the > label will belong to the toggle button div itself and with the new version > of Bootstrap-toggle, the role="button" is already there, so no need to add > it. > > I have tested this patch on Mac with VoiceOver (on which I could reproduce > the issue) and it is working fine. > > After committing this patch, we need to provide the nightly build link to > the author of this RM, so he can test with a Braille display. > > Thanks, > Khushboo > > > -- *Thanks & Regards* *Akshay Joshi* *pgAdmin Hacker | Principal Software Architect* *EDB Postgres * *Mobile: +91 976-788-8246* --000000000000ef621a05bddda45e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks, patch applied.

On Wed, Mar 17, 2021 at 2:36 PM Khus= hboo Vashi <khushboo.= vashi@enterprisedb.com> wrote:
Hi,

Please find t= he attached patch to fix the RM #6317:=C2=A0 Toggle buttons are inaccessibl= e.

Our toggle buttons are not the HTML buttons but= the combinations of HTML tags which function as a toggle button. As the to= ggle button itself doesn't have a label/title as it wrapped around a di= v, we have provided the extra hidden label above the toggle button div, so = on receiving the focus, toggle button will read the label we provided(For e= xample: "Can login?, Yes, Toggle. Button''), which was working= as expected with Chrome Screen Reader extension, on which we have tested. = Unfortunately, most screen readers like VoiceOver, NVDA etc.. read the labe= l and the button as different tags, so when the label gets the focus, the s= creen reader reads it as "Can login? Yes, Toggle Button", and whe= n we try to click it, we can't, as it is just a label.=C2=A0
=
To fix this issue, I have put the label inside the toggle di= v, so the label will belong to the toggle button div itself and with the ne= w version of Bootstrap-toggle, the role=3D"button" is already the= re,=C2=A0 so no need to add it.

I have tested this= patch on Mac with VoiceOver (on which I could reproduce the issue) and it = is working fine.

After committing=C2=A0this patch,= we need to provide the nightly build link to the author of this RM, so he = can test with a Braille display.

Thanks,
Khushboo




--
Thanks & Regards
Akshay Joshi
pgAdmi= n Hacker | Principal Software Architect
EDB Postgres
Mobile: +91 976-788-8246

--000000000000ef621a05bddda45e--