Closed Bug 273099 Opened 21 years ago Closed 21 years ago

Device Independence

Categories

(Core :: SVG, defect)

Product:
Core
Component:
SVG
Platform:
PowerPC
All
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: jay, Unassigned)

Details

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a5) Gecko/20041103 Firefox/0.9.1+ Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a5) Gecko/20041103 Firefox/0.9.1+ The User Agent Guidelines* state: Guideline 1. Support input and output device-independence. There is no means to navigate SVG documents via the keyboard, or afaik any other device than a mouse. This is a fundamental accessibility requirement: * http://www.w3.org/TR/UAAG10/guidelines.html#gl-device-independence User Agent Accessibility Guidelines 1.0 "This document provides guidelines for designing user agents that lower barriers to Web accessibility for people with disabilities (visual, hearing, physical, cognitive, and neurological). User agents include HTML browsers and other types of software that retrieve and render Web content." Reproducible: Always Steps to Reproduce: 1. 2. 3. Expected Results: The user agent should Support input and output device-independence. jwatt, The Document Object Model (DOM) Level 3 Events Specification does not mention keyboard navigation, which is strange, so I've emailed a request regarding this to the working group: http://lists.w3.org/Archives/Public/www-dom-ts/2004Dec/0001.html (i've assumed this uri) As Martin Honnen recently asserted "Even DOM Level 3 hasn't managed to have key events as a W3C recommendation, there is only a note of the DOM Level 3 events": http://groups.yahoo.com/group/svg-developers/message/46366 This is a real and urgent concern. I am continually being asked why SVG does not provide device independence. In particular screen readers and other enabling technologies can and will not be conceived, designed and deployed until this is resolved satisfactorily.
As far as I can tell, you can navigate an SVG fragment just like an HTML fragment: cursor keys pan, tab moves focus, enter follows links. In fact I can't see anything that the mouse pointer can do that the keyboard can't. No?
Summary: Device Independence → Keyboard access to SVG (Device Independence)
Besides that, this isn't a valid bug report. You need to specify *details* on what we do wrong, or what we don't do that you think we should. Saying "the user agent should support input and output device-independence" is too vague. With regards to DOM3 keyboard events, what do you need over and above: http://www.w3.org/TR/DOM-Level-3-Events/events.html#Events-TextEvents-Interfaces http://www.w3.org/TR/DOM-Level-3-Events/events.html#Events-KeyboardEvents-Interfaces I haven't looked at that thread you linked to yet, but will do later. Nevertheless, it would be preferable to have details on what you want in your reports.
hixie wrote "tab moves focus" please can you suggest how? do you have an example document? I have visited numerous svg pages, yet not found one that responds to a tab key event. (are you referring to SVG in HTML documents?) -- whoever changed the summary please don't. Keyboard access, was merely one example, there are numerous other alternative input and output devices, separate bugs can be filed for each of these. This one will depend on each of them. This bug report provides a useful locus for monitoring compliance with UAG 1.
Summary: Keyboard access to SVG (Device Independence) → Device Independence
If you have specific bugs, please file those. However, there is no point having a "meta bug" which doesn't actually refer to a single issue. I have filed bug 273197 specifically on the tabbing issue. Thanks for pointing that one out. Please follow the form I have used in that bug when filing new bugs. There is no point filing a bug that doesn't have very clear steps to reproduce and a very clear way of determining if the bug is fixed or not.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.