E-mail List Archives

Search E-mail List Archives for

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

From: Don Raikes
Date: Mon, Sep 30 2019 3:03PM
Subject: VoiceOver ignoring WCAG 1.3.1 and 2.4.2
No previous message | Next message →

Hello,



I have been doing some mobile web testing in preparation for a demo, and have discovered a couple of issues with VoiceOver and I want to know if others have seen the problems:



1. When navigating tables, VoiceOver is not reading column headers even though the table is properly marked up using scope="col" attributes.

2. VoiceOver is not announcing page titles when there is a full or partial page refresh and the title changes.

System configurations:

iPhone 8 with iOS 13.1.1

iPad mini with iPadOS 13.1.2



These two requirements seem pretty basic so I would expect VoiceOver to respect them.



--
Thanks, Donald

"As a leader, to be successful, is to help the people around you to be successful." - Kent Boucher



Accessibility, like security, is better when built-in from the beginning rather than bolted on at the end.


http://www.oracle.com/
Donald Raikes | Accessibility Specialist
Mobile: HYPERLINK "tel:+15202717608"+15202717608 | VOIP: HYPERLINK "tel:+15205744033"+15205744033
Oracle Accessibility Program Office
| Tucson, Arizona

http://www.oracle.com/commitment

Oracle is committed to developing practices and products that help protect the environment

From: Steve Green
Date: Mon, Sep 30 2019 3:11PM
Subject: Re: VoiceOver ignoring WCAG 1.3.1 and 2.4.2
← Previous message | Next message →

Column headers have always worked fine for me. I just confirmed this with iOS 12.1 on an iPhone 6S+

Can you share a link to a page where they are not announced?

Steve Green
Managing Director
Test Partners Ltd

From: Patrick H. Lauke
Date: Mon, Sep 30 2019 3:15PM
Subject: Re: VoiceOver ignoring WCAG 1.3.1 and 2.4.2
← Previous message | Next message →

Just picking up on the subject line, I'd comment here that WCAG SCs are
requirements on the content. An AT doesn't "ignore" WCAG SCs, the same
way it doesn't pass or fail SCs. They're not requirements on user agents/AT.

P
--
Patrick H. Lauke

www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke

From: Don Raikes
Date: Mon, Sep 30 2019 3:23PM
Subject: Re: Steve, VoiceOver ignoring WCAG 1.3.1 and 2.4.2
← Previous message | Next message →

H
Ttp://donraikes.github.io/demo?root=structure

This page has two tables near the bottom of the page. The first table is a simple table that utilizes scope="col" while the second utilizes ids in the headers and headers attribute in the datga cells.

This page was written using the OracleJET framework, and that may be the p0roblem, which is why I wanted to ask others their opinions.

From: Steve Green
Date: Mon, Sep 30 2019 4:20PM
Subject: Re: Steve, VoiceOver ignoring WCAG 1.3.1 and 2.4.2
← Previous message | Next message →

There's something very odd going on. I am seeing the same issue as you, whereby the column headers are not announced on your test page. However, when I copied the html for your table into a test page and hosted it on one of our servers at http://tpl1.com/tables.htm, the column headers are announced correctly. I can't see anything in the CSS on your page that would cause this, and there don't appear to be any JavaScript event handlers that would cause it either.

Even more odd is that the row headers are announced correctly on your test page if vertical navigation is enabled in the rotor.

Steve

From: Don Raikes
Date: Mon, Sep 30 2019 6:12PM
Subject: Re: Steve, VoiceOver ignoring WCAG 1.3.1 and 2.4.2
← Previous message | Next message →

Steve,

I agree. I have wondered if there is something unusual in the way the html is nested with the OracleJET page construction to cause this problem.

Thanks for checking this out for me.

From: Steve Green
Date: Mon, Sep 30 2019 11:50PM
Subject: Re: Steve, VoiceOver ignoring WCAG 1.3.1 and 2.4.2
← Previous message | No next message

I don't see anything unusual in the html, and the Accessibility tab in Chrome developer tools shows that the role is correct for all the elements in the table. To dig deeper, you would need to use the Safari Web Inspector to view and modify the DOM on a Mac, but I don't have time to do that.

Steve