Bug 266458

Summary:	AX: "VoiceOver Accessibility Issues with Custom Grids and Table Markup"
Product:	WebKit	Reporter:	Hyongsop Kim <khsbory>
Component:	Accessibility	Assignee:	Nobody <webkit-unassigned>
Status:	NEW ---
Severity:	Critical	CC:	andresg_22, tyler_w, webkit-bug-importer
Priority:	P2	Keywords:	InRadar
Version:	WebKit Nightly Build
Hardware:	iPhone / iPad
OS:	iOS 17

Description Hyongsop Kim 2023-12-14 21:45:27 PST

I am writing to report an issue concerning the accessibility of custom grids in web development. When elements like div and span are designed in a grid format, we can enhance accessibility by using attributes such as role grid, row, columnheader, and gridcell. Additionally, even in cases where a table is marked up with the table tag, it may be necessary to implement accessibility by setting the td cell’s role to none and treating elements like buttons within as gridcells.
However, there is a significant problem with how VoiceOver currently handles the grid and gridcell attributes. The issues are as follows:
1.
When the td cells within a table tag are set to role none and the nested buttons are treated as gridcells, VoiceOver fails to properly process the role none attribute. This results in an error where it cannot read the connected column titles when reading each cell's data, and also incorrectly outputs the row and column numbers.
2.
When using a custom grid with gridcell applied, if styles used in table properties are applied, VoiceOver fails to correctly output the gridcell information.
To demonstrate these issues, we have implemented three sample tables. Each table includes an explanation of the problem it illustrates. We request you to test these with VoiceOver and provide a solution for the identified issues.
Thank you for your attention to this matter.
You can find the tables and their descriptions at: https://khsruru.com/calendar/.

Comment 1 Radar WebKit Bug Importer 2023-12-14 21:45:38 PST

<rdar://problem/119704723>

Comment 2 Tyler Wilcock 2024-03-04 10:33:51 PST

Hey! Thanks for filing this bug. Looks like your link leads to a 404. Would it be possible to attach these minimal HTML table reproduction cases as attachments here?