Member Avatar for DaMutant

Hello everyone, I would like to apologize now for my ignorance regarding W3C and 508 Compliance. "I'm Sorry I am ignorant in the matters of ADA web compliance. I just inherited these duties without any training or knowledge of the rules around the compliance question."

I have searched high and low and far and wide but could not find what I needed to know.

Here is what I have to ask. In the case of message boxes such as ones that may ask the simple question, "Are you sure you want to cancel this session?", or something to that effect; are they required to be W3C, 508, and whatever else may be out there compliant?

Thank you and any assistance on this would be greatly appreciated.

DaMutant (Doug)

  • 2 Contributors
  • 5 Replies
  • 85 Views
  • 7 Hours Discussion Span
  • Latest Post Latest Post by teedoff

Dani AI

Generated

Short answer for (and following 's remark about validation): HTML validation (what the W3C validator checks) is not the same as accessibility compliance. If your project is required to meet accessibility rules (WCAG / Section 508 where applicable) then message boxes and confirmation dialogs must be implemented so people using keyboards and assistive tech can use them safely and predictably.

Key implementation points to make a message box accessible:

  • Ensure keyboard operability: open with keyboard, support Tab/Shift+Tab, and allow Escape to close.
  • Use appropriate semantics: prefer the native <dialog> when it fits; otherwise follow WAI-ARIA patterns (use role="dialog" or role="alertdialog", aria-labelledby, aria-describedby).
  • Manage focus: move focus into the dialog on open, trap focus while open, and restore focus to the element that opened it on close.
  • Indicate modality and hide page content from AT: use aria-modal="true" and mark background content aria-hidden="true" or use inert techniques so screen readers do not read the page behind the dialog.
  • Make actions clear and safe: label buttons descriptively (avoid ambiguous "OK"), and ensure visual focus styles and sufficient contrast.

Test with keyboard-only workflows, a screen reader (NVDA or VoiceOver), and automated checks (axe, WAVE). For detailed patterns and success criteria see the WAI-ARIA dialog guidance and WCAG keyboard/focus criteria: WAI-ARIA Authoring Practices — dialog pattern and WCAG quick reference (keyboard & focus).

Recommended Answers

All 5 Replies

Member Avatar for teedoff

Have you validated your code at W3C and received errors?

Member Avatar for DaMutant

Actually, what I calidated was successful but then this question arose. The thought is that it is a requirement of ours that a message box should meet that W3C standard and not necessarily a W3C requirement. I am trying determine if it is both?

Member Avatar for teedoff

So your company/client requires W3C validation? I would say 90% of webpages on the web DONT validate completely...lol Although I guess most professional web design houses require code to validate. Havent dealt with message boxes much, so not sure about your specific issue. Does W3C website have anything to read up on them?

lol just validated amazon.com home page and it had over 1100 warnings and over 100 erros! Just thought I'd add that.

Edited by teedoff because: n/a
Member Avatar for DaMutant

Yes we require W3C validation. I didn't see anything on that site. I have been looking everywhere. I'll keeep on looking at it and see if I can get lucky. I do appreciate your responses and your time. Thank you very much.

Member Avatar for teedoff

No problem, sorry I couldnt have been more help. Someone here I know will be able to give you some great answers. Good Luck!

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.