Repository navigation
Closed functionality within web content? #5433
Replies: 7 comments 8 replies
|
One example if an author were to create their own keyboard in the web app and not accept input for some functionality from anything but that keyboard (e.g. not the regular keyboard interface provided by the browser passing keystrokes on from the platform keyboard interface) then that would that/those functionality(s) would be closed. |
|
I would be reluctant to rule out closed functionality in web content categorically. The definition of closed functionality in EN 301 549 (chapter 3.1) is technology-neutral: it refers to functionality whose characteristics prevent a user from attaching, installing or using assistive technology. Furthermore, chapter 5.1.2.1 and 5.1.2.2 explicitly address ICT that includes closed functionality. Annex A.2.5 lists these requirements under “All ICT”. I therefore do not see a normative basis for assuming that a website or a web application can never include closed functionality. Of course, this does not mean that every inaccessible component or every failure to expose information through accessibility APIs should be classified as closed functionality. There is an important distinction between a component that is simply inaccessible or incorrectly implemented, and functionality whose technical characteristics actually prevent the use of assistive technology. Some possible examples in the context of an actual website opened in a web browser might be:
However, in 99% of all web tests, the Chapter 5.1 criteria could be marked as “not applicable.” |
|
if you have a keyboard on screen that you have to tab to and his spacebar to type a character -- that would NOT meet the "keyboard interface" requirement. "keyboard interface" is the plain language version of "keyboard input api" which is what is required. g |
|
I see another problem here, which appears to be a fundamental design flaw in the EN standard. For closed desktop software, it is clearly defined which requirements from chapter 5.1 and which from chapter 11 apply (5.1.2.1: "The requirements within this clause replace those in clauses 5.2 to 13 that specifically state that they do not apply to closed functionality."). For websites, documents, hardware, etc., this is not specified. That means that all requirements from 5.1 as well as all requirements from the respective chapter (8, 9, 10) apply to closed functionality, even though the requirements from chapter 5.1 are intended to supersede certain requirements from the other chapters. This allows for two different interpretations:
|
|
@JAWS-test 5.1 does not supersede anything. They apply to a particular functionality if that functionality in a product is closed. Other provisions continue to apply unless it is stated that they do not apply to that functionality. Non-web documents that have active code in them - are software - or at least that functionality falls into that category. And note that there are no en 301 549 provisions for documents -- only for Non-web documents. Web apps are software -- but en 301 549 has no provisions for software -- only for non-web software. This prevents there from being ambiguity between the Web section and the non-web software section. OTHER NOTE
Does this help? if not perhaps give specific examples of something where you see a conflict. thanks |
|
@GreggVan Thanks for your response. However, I think we may be talking past each other. My original point was not that clause 5.1 generally supersedes requirements from other clauses. I explicitly referred to the replacement of certain requirements, as stated in Note 2 of 5.1.2.1. The issue I am raising is precisely that this replacement mechanism is explicitly reflected in several requirements in clause 11, but not in the corresponding requirements in clause 9. Let me give a concrete example:
My question is: What happens to requirements such as 9.1.3.1, 9.1.3.2, 9.1.3.5, 9.4.1.2 and 9.4.1.3 in this situation? Unlike several requirements in clause 11, these requirements do not contain an explicit exception for closed functionality or an alternative requirement referring to clause 5.1. I understand your point that requirements from other clauses continue to apply unless they explicitly state otherwise. But this is exactly the problem I am trying to highlight: the standard explicitly addresses this interaction for certain requirements in clause 11, but does not do so for the corresponding requirements in clause 9. So how is this intended to work? Are the requirements of clause 9 supposed to apply without exception, even when the ICT environment has closed functionality that prevents assistive technologies from accessing the relevant information? |
|
the reason 9 does not cover a computer that is locked down is that 9 deals with web content -- and the web content is not locked down. It is the computer that is locked down - and its software (the platform under the web browser). So 9 is not responsible for that and the web author is not either. it is the software (clause 11) or the processes of the location that closed the computer and they are responsible for meeting all the closed functionality provisions. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I wonder whether there can be types of content with closed functionality (users' AT not available) within web content, or whether closed functionality would only come into play in cases where functionality, say, in web applications involves the use of hardware with closed functionality (e.g. a connected card reader with a number pad and a small display, or another ancillary device).
Any views on this?
All reactions