RE: Should we add keyboard focus to headings/text/non-linked images?

Katherine

My 2 cents worth.

I think what you have touched upon should be a browser functionality. Not a web page functionality. By doing this, this provides the functionality on all pages with correct mark-up. Thus a shortcut is provided in the browser for the pure keyboard user who has vision to jump to different sections on the page.

Screen readers developed the method of jumping to specific elements within a page because the browser did not have the feature and the users requested it, to make surfing the net easier.


[https://www.cisco.com/c/dam/m/en_us/signaturetool/images/banners/standard/02_standard_ciscoblue02.png]




Sean Murphy
SR ENGINEER.SOFTWARE ENGINEERING
seanmmur@cisco.com<mailto:seanmmur@cisco.com>
Tel: +61 2 8446 7751










Cisco Systems, Inc.
The Forum 201 Pacific Highway
ST LEONARDS
2065
Australia
cisco.com



[http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif]

Think before you print.

This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.
Please click here<http://www.cisco.com/c/en/us/about/legal/terms-sale-software-license-agreement/company-registration-information.html> for Company Registration Information.







From: Katherine Shaw <katherine@prometsource.com>
Sent: Tuesday, 5 March 2019 7:31 AM
To: w3c-wai-ig@w3.org
Subject: Should we add keyboard focus to headings/text/non-linked images?

I have a question regarding guideline 2.1.1 Keyboard. Should headings, sections of text, and/or non-linked images also receive keyboard focus? I wonder about this for users that use a keyboard exclusively without a mouse, and don't use a screen reader.

I ask this because according to the W3 documentation at https://www.w3.org/TR/UNDERSTANDING-WCAG20/keyboard-operation-keyboard-operable.html, it says "All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints."

It also mentions: "Keyboard emulators include speech input software, sip-and-puff software, on-screen keyboards, scanning software and a variety of assistive technologies and alternate keyboards. Individuals with low vision also may have trouble tracking a pointer and find the use of software much easier (or only possible) if they can control it from the keyboard."

I'd love your input. Thanks.

Katherine Shaw