WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: WebAIM-Forum Digest, Vol 166, Issue 27

for

From: Peter Shikli
Date: Jan 31, 2019 1:27PM

Message 12 to 14 seem to have been cropped from this email posting. Please send.
Cheers,
Peter Shikli

----------------------------------------
From: <EMAIL REMOVED>
Sent: 1/31/19 11:00 AM
To: <EMAIL REMOVED>
Subject: WebAIM-Forum Digest, Vol 166, Issue 27
Send WebAIM-Forum mailing list submissions to
<EMAIL REMOVED>

To subscribe or unsubscribe via the World Wide Web, visit
http://list.webaim.org/mailman/listinfo/webaim-forum
or, via email, send a message with subject or body 'help' to
<EMAIL REMOVED>

You can reach the person managing the list at
<EMAIL REMOVED>

When replying, please edit your Subject line so it is more specific
than "Re: Contents of WebAIM-Forum digest..."

Today's Topics:

1. Beyonc?'s website in class-action lawsuit ( <EMAIL REMOVED> )
2. Using required attribute with a star mark VS Marking as
optional (Ramakrishnan Subramanian)
3. Re: Using required attribute with a star mark VS Marking as
optional (Graham Armfield)
4. Re: Native or web? (Mohith BP)
5. Re: Using required attribute with a star mark VS Marking as
optional (Isabel Holdsworth)
6. Re: Accessible, flexible select box (Isabel Holdsworth)
7. Re: Accessible, flexible select box (Isabel Holdsworth)
8. Re: Accessible, flexible select box ( <EMAIL REMOVED> )
9. Colour contrast and blue light filters (Pat Reynolds)
10. Re: Colour contrast and blue light filters (Patrick H. Lauke)
11. Re: Accessible, flexible select box (Isabel Holdsworth)
12. Re: Using required attribute with a star mark VS Marking as
optional (Birkir R. Gunnarsson)
13. Re: Colour contrast and blue light filters (Jonathan Avila)
14. Accessibility UI developers needed in CA, US (Jeevan Reddy)

----------------------------------------------------------------------

Message: 1
Date: Wed, 30 Jan 2019 16:24:45 -0500
From:
To: "'WebAIM Discussion List'"
Subject: [WebAIM] Beyonc?'s website in class-action lawsuit
Message-ID: <013001d4b8e2$391600d0$ab420270$@pubcom.com>
Content-Type: text/plain;charset="iso-8859-1"

Didn?t see this posted on the list.

Beyonc??s website cited for lack of accessibility.

News story is here:
https://musically.com/2019/01/07/beyonces-company-sued-over-the-accessibilit
y-of-her-website/

? ? ?

Bevi Chagnon, founder/CEO |

? ? ?

PubCom: Technologists for Accessible Design + Publishing

consulting ? training ? development ? design ? sec. 508 services

Upcoming classes at www.PubCom.com/ www.pubcom.com/classes=""> classes

? ? ?

------------------------------

Message: 2
Date: Thu, 31 Jan 2019 11:58:10 +0530
From: Ramakrishnan Subramanian
To: <EMAIL REMOVED>
Subject: [WebAIM] Using required attribute with a star mark VS Marking
as optional
Message-ID:

Content-Type: text/plain; charset="UTF-8"

Hi Team,
I would like to listen to your opinion on the following:
Marking the mandatory fields with the ?star mark and required
attribute? VS marking as ?optional? for the optional fields.
We know that the ideal recommendation for a form is to mark the
mandatory fields with the ?star mark? and with the ?required
attribute?. But, Instead of that, when the other practice is followed,
what are the pros and cons? And whether this practice is considered
WCAG compliant?

--

Thanks and Regards
Ramakrishnan

------------------------------

Message: 3
Date: Thu, 31 Jan 2019 08:14:50 +0000
From: Graham Armfield
To: WebAIM Discussion List
Subject: Re: [WebAIM] Using required attribute with a star mark VS
Marking as optional
Message-ID:

Content-Type: text/plain; charset="UTF-8"

Hi Ramakrishnan,

My own view is that it doesn't matter which way you do it as long as users
know what's going on.

The 'convention' of indicating required fields with a * goes back at least
to the early 2000s when I started building web things professionally. As
far as I am aware all screen readers announce the asterisk (*) as 'Star'
when in a page in English, but best to include it in the element
though. And it's also a good idea to have a message at the top of the form
that reads "Required data is marked with *" or similar.

Lately, probably as a result of the onset of greater scrutiny around
privacy, online forms are asking only for the data they really need. So the
tendency is much more that most input fields are required. So the reverse
approach of saying "All data fields are required, unless indicated." at the
top of the form seems much more common now.

Using the 'required' attribute does mean that screen readers announce the
field as required. However, I'm not a big fan of the default error messages
generated by browsers. In Firefox the "Please fill out this field" message
(and screen reader announcement) is just not specific enough - especially
if there are multiple required fields that have not been completed.

So I favour the use of aria-required="true" on the inputs, and some more
robust client-side validation that generates more meaningful error
messages, and also adds aria-invalid="true" to the input element if errors
are detected.

The challenge comes around radio button groups where the error might be
that the user hasn't selected one of the options, rather than the
individual options themselves. Is aria-required appropriate there I wonder?
Maybe a required message in the ?

Regards
Graham Armfield
coolfields.co.uk www.coolfields.co.uk/="">
M:07905 590026
T: 01483 856613
@coolfields

------------------------------

Message: 4
Date: Thu, 31 Jan 2019 14:27:57 +0530
From: Mohith BP
To: WebAIM Discussion List
Subject: Re: [WebAIM] Native or web?
Message-ID:

Content-Type: text/plain; charset="UTF-8"

Hi Barry,

You have mentioned:
"I was concerned that it
was an app written for IOS and probably uses java to emulate the gestures
used by a IOS device, but I'm concerned whether or not it will use the VO
gestures."

It is highly recommended to test with screen reader turned on to
verify that there are no custom gestures created, the gestures are not
interfering with the VO gestures and finally all the actions can be
performed without the specific gestures when screen reader is turned
off as per WCAG 2.1 SC 2.5.1:
2.5.1 Pointer Gestures:
All functionality that uses multipoint or path-based gestures for
operation can be operated with a single pointer without a path-based
gesture, unless a multipoint or path-based gesture is essential.
(Level A)

Note:
This requirement applies to web content that interprets pointer
actions (i.e. this does not apply to actions that are required to
operate the user agent or assistive technology).

Thanks & Regards,
Mohith B. P.

On 1/30/19, Jonathan Avila wrote:
> One trick I use to see if something is a webview or not is to look at the
> Voice Over rotor settings in iOS when focused on the content in question and
> see if there are HTML type rotor settings for links, lists, form controls,
> table, etc. If so you are in a webview.
>
> Jonathan
>
> Jonathan Avila, CPWA
> Chief Accessibility Officer
> Level Access
> <EMAIL REMOVED>
> 703.637.8957 office
>
> Visit us online:
> Website?|?Twitter?|?Facebook?|?LinkedIn?|?Blog
>
> Looking to boost your accessibility knowledge? Check out our free webinars!
>
> The information contained in this transmission may be attorney privileged
> and/or confidential information intended for the use of the individual or
> entity named above. If the reader of this message is not the intended
> recipient, you are hereby notified that any use, dissemination, distribution
> or copying of this communication is strictly prohibited.
>
>