4.1.2 Name, Role, Value VS an unlabeled nav

Hi,

I would value advice on whether the following is a WCAG fail.

4.1.2 Name, Role, Value (https://www.w3.org/TR/WCAG20/#ensure-compat-rsv​) states:

> For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined...

How to meet (https://www.w3.org/WAI/WCAG21/quickref/?versions=2.0#qr-ensure-compat-rsv) "Failures" list includes:

> F68: Failure of Success Criterion 4.1.2 due to a user interface control not having a programmatically determined name

I have a page with three navigation areas
1). a "Quick links" area (top-right for visual users, change language link, Contact, etc)
2). main nav
3). a FOOTER with seven or so utility links

All do not use HTML NAV (via NAV tag or ROLE delcared).

All are not labelled.

I propose to fail this, based on 4.1.2, and note F68 as one concrete reason.

However, 4.1.2 states
> For all user interface components (including but not limited to: form elements, links...
and F68 states
> F68: Failure of Success Criterion 4.1.2 due to a user interface control not having a programmatically determined name...

Does the language "interface components" in 4.1.2 mean that F68 does not apply since*it* talks of "...a user interface control...". Components VS Control?

Thanks for any comments.

Regards,

Alan

-Alan Bristow
Web Programmer
Elections Canada
alan.bristow@elections.ca

Received on Tuesday, 2 February 2021 14:31:37 UTC