E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 7 (In chronological order)

From: Sumit Patel
Date: Tue, Aug 31 2021 4:49AM
Subject: Accessibility of Signature Text Editor
No previous message | Next message →

Hi all,

I have a text editor which used to do the signature on web. We do not
have any alternative for the keyboard-only and screen reader users.
How to make it accessible ?
Any idea?

Regards,
Sumit.

From: glen walker
Date: Tue, Aug 31 2021 9:00AM
Subject: Re: Accessibility of Signature Text Editor
← Previous message | Next message →

Are you talking about signing a document with a signature where you drag
the mouse to write your name?

I saw an example recently where the signature was a tab widget. One tab
had an area where you could drag your mouse to sign your name and the other
tab had an input field where you could type your name and it would generate
a "signature" for you. The UI could use a little work because the field to
type your name was always visible so it was a little confusing that you
could type your name and sign with the mouse. The field should only be
visible if the second tab was chosen.

I'm attaching two pics of the two tabs as described above.

[image: First tab shows an area where you can drag your mouse to sign your
name.]


[image: Second tab shows a field where you can type your name and a
secondary area where the signature is generated using a script type font.]

On Tue, Aug 31, 2021 at 4:49 AM Sumit Patel < = EMAIL ADDRESS REMOVED = >
wrote:

> Hi all,
>
> I have a text editor which used to do the signature on web. We do not
> have any alternative for the keyboard-only and screen reader users.
> How to make it accessible ?
> Any idea?
>
> Regards,
> Sumit.
> > > > >

From: Sumit Patel
Date: Tue, Aug 31 2021 11:03PM
Subject: Re: Accessibility of Signature Text Editor
← Previous message | Next message →

Here, I do not have any input field where I can type my name as
signature. I have only 1 area where I can draw the sign using mouse.

On 31/08/2021, glen walker < = EMAIL ADDRESS REMOVED = > wrote:
> Are you talking about signing a document with a signature where you drag
> the mouse to write your name?
>
> I saw an example recently where the signature was a tab widget. One tab
> had an area where you could drag your mouse to sign your name and the other
> tab had an input field where you could type your name and it would generate
> a "signature" for you. The UI could use a little work because the field to
> type your name was always visible so it was a little confusing that you
> could type your name and sign with the mouse. The field should only be
> visible if the second tab was chosen.
>
> I'm attaching two pics of the two tabs as described above.
>
> [image: First tab shows an area where you can drag your mouse to sign your
> name.]
>
>
> [image: Second tab shows a field where you can type your name and a
> secondary area where the signature is generated using a script type font.]
>
> On Tue, Aug 31, 2021 at 4:49 AM Sumit Patel < = EMAIL ADDRESS REMOVED = >
> wrote:
>
>> Hi all,
>>
>> I have a text editor which used to do the signature on web. We do not
>> have any alternative for the keyboard-only and screen reader users.
>> How to make it accessible ?
>> Any idea?
>>
>> Regards,
>> Sumit.
>> >> >> >> >>
> > > > >

From: glen walker
Date: Thu, Sep 02 2021 2:42PM
Subject: Re: Accessibility of Signature Text Editor
← Previous message | Next message →

I was showing you a nice example of something that passes WCAG 2.5.1.

If you don't have an alternate way for a user to provide their signature,
then it *might* be a failure of 2.5.1. It depends if the act of signing is
considered "essential". That is, I'm sure some kind of signature is
essential but does it have to be a mouse drawn signature? That's not a
question I can answer. It depends on your situation.

On Tue, Aug 31, 2021 at 11:03 PM Sumit Patel < = EMAIL ADDRESS REMOVED = >
wrote:

> Here, I do not have any input field where I can type my name as
> signature. I have only 1 area where I can draw the sign using mouse.
>
>

From: Sherman, Joseph
Date: Tue, Sep 28 2021 10:57AM
Subject: Re: accessibility of Select element in iOS 15 and Safari
← Previous message | Next message →

-

From: Steve Green
Date: Tue, Sep 28 2021 12:33PM
Subject: Re: accessibility of Select element in iOS 15 and Safari
← Previous message | Next message →

I cannot verify what you are seeing, but I do not regard it as a WCAG non-conformance if a user agent is displaying colours that you did not (and perhaps cannot) specify. It's a failure of the user agent, not the website.

Steve Green
Managing Director
Test Partners Ltd


-----Original Message-----
From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = > On Behalf Of Sherman, Joseph
Sent: 28 September 2021 17:58
To: = EMAIL ADDRESS REMOVED =
Subject: [WebAIM] accessibility of Select element in iOS 15 and Safari

I just updated to iOS 15 on my iPhone and noticed a possibe accessibility issue of concern. The default colors for dropdown pickers in iOS 15 Safari seems to have changed to a blue on grey color scheme, as in the below. This color scheme has does not have the 4.5:1 contrast ratio required by WCAG AA guidelines. An example is page: https://www.w3schools.com/tags/tryit.asp?filename=tryhtml_select. The issue appears to be with the select element. I tried the accessibility settings and only invert color made a difference. The other options did not change the issue. Can anyone confirm this or is it just me?

Thanks,

[cid:image001.png@01D7B44F.4A5FD710]

Joseph Sherman
Digital Access Coordinator
= EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >
Text and Cell 503-865-6812
[Office of Equity and Human Rights]

The City of Portland ensures meaningful access to City programs, services, and activities to comply with Civil Rights Title VI and ADA Title II laws and reasonably provides: translation, interpretation, modifications, accommodations, alternative formats, auxiliary aids and services. To request these services, contact 503-823-2709, City TTY 503-823-6868, Relay Service: 711

Traducción e Interpretación | Biên Dịch và Thông Dịch | अनुवादन तथा व्याख्या
口笔译服务 | Устный и письменный перевод | Turjumaad iyo Fasiraad
Письмовий і усний переклад | Traducere și interpretariat | Chiaku me Awewen Kapas
Translation and Interpretation: 503-823-2709

From: Sherman, Joseph
Date: Wed, Sep 29 2021 6:11PM
Subject: Re: accessibility of Select element in iOS 15 and Safari
← Previous message | No next message

I am not looking to fail the website, I am looking to confirm so I can send a bug report to Apple, thanks.

Joseph Sherman
Digital Access Coordinator
= EMAIL ADDRESS REMOVED =
Text and Cell 503-865-6812

 
The City of Portland ensures meaningful access to City programs, services, and activities to comply with Civil Rights Title VI and ADA Title II laws and reasonably provides: translation, interpretation, modifications, accommodations, alternative formats, auxiliary aids and services. To request these services, contact 503-823-2709, City TTY 503-823-6868, Relay Service: 711
 
Traducción e Interpretación  |  Biên Dịch và Thông Dịch  |  अनुवादन तथा व्याख्या
口笔译服务  |  Устный и письменный перевод  |  Turjumaad iyo Fasiraad
Письмовий і усний переклад  |  Traducere și interpretariat  |   Chiaku me Awewen Kapas
Translation and Interpretation:  503-823-2709

-----Original Message-----
From: Steve Green < = EMAIL ADDRESS REMOVED = >
Sent: Tuesday, September 28, 2021 11:34 AM
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
Subject: Re: [WebAIM] accessibility of Select element in iOS 15 and Safari

I cannot verify what you are seeing, but I do not regard it as a WCAG non-conformance if a user agent is displaying colours that you did not (and perhaps cannot) specify. It's a failure of the user agent, not the website.

Steve Green
Managing Director
Test Partners Ltd


-----Original Message-----
From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = > On Behalf Of Sherman, Joseph
Sent: 28 September 2021 17:58
To: = EMAIL ADDRESS REMOVED =
Subject: [WebAIM] accessibility of Select element in iOS 15 and Safari

I just updated to iOS 15 on my iPhone and noticed a possibe accessibility issue of concern. The default colors for dropdown pickers in iOS 15 Safari seems to have changed to a blue on grey color scheme, as in the below. This color scheme has does not have the 4.5:1 contrast ratio required by WCAG AA guidelines. An example is page: https://www.w3schools.com/tags/tryit.asp?filename=tryhtml_select. The issue appears to be with the select element. I tried the accessibility settings and only invert color made a difference. The other options did not change the issue. Can anyone confirm this or is it just me?

Thanks,

[cid:image001.png@01D7B44F.4A5FD710]

Joseph Sherman
Digital Access Coordinator
= EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >
Text and Cell 503-865-6812
[Office of Equity and Human Rights]

The City of Portland ensures meaningful access to City programs, services, and activities to comply with Civil Rights Title VI and ADA Title II laws and reasonably provides: translation, interpretation, modifications, accommodations, alternative formats, auxiliary aids and services. To request these services, contact 503-823-2709, City TTY 503-823-6868, Relay Service: 711

Traducción e Interpretación | Biên Dịch và Thông Dịch | अनुवादन तथा व्याख्या
口笔译服务 | Устный и письменный перевод | Turjumaad iyo Fasiraad
Письмовий і усний переклад | Traducere și interpretariat | Chiaku me Awewen Kapas
Translation and Interpretation: 503-823-2709