W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2016

Question regarding the responsive web

From: Tanaka, Satoko <sako-t@jp.fujitsu.com>
Date: Thu, 7 Jul 2016 04:43:07 +0000
To: "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Message-ID: <BEC8082DDC8CFF4797A2490179010BAB6EA67073@G01JPEXMBKW04>

I have a question about SC 1.3.2. It would be highly appreciated, if someone would give me a good advice.

Recently a lot of websites use “the responsive web” for mobile devices. In the responsive web, the web page has some break points which are a trigger to change the page layout even the HTML source code has no change.
In mobile layout, some items could move to a different position from PC appearance. If an item is placed differently between PC layout and mobile layout, and the position of the item in mobile environment does not match with the order in the source code. (In PC layout, the order and item’s visual position is the same)
In this case, can I regard it as sufficient against SC 1.3.2 in WCAG 2.0?

For instance, a functional element which change the website language is placed in a header area in PC layout. However, in a smartphone layout, the language changer move into footer area. The HTML source code is the same, so the order of the item in the source code is always the same.
In this case, the web page meet the requirement of SC 1.3.2 or not?

In the Understanding document of SC 1.3.2, a technique about DOM order and layout is listed as a sufficient technique; C27. It says “The objective of this technique is to ensure that the order of content in the source code is the same as the visual presentation of the content.”
Does a web page have to meet this technique C27, even if it uses responsive web technology in mobile? Should I apply WCAG 2.0 not only for PC, but also for mobile accessibility evaluation?

I really need your help. If someone would give me a clear answer, it would be highly appreciated. Thanks in advance.

Many thanks and kind regards,
Received on Thursday, 7 July 2016 04:43:47 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 7 July 2016 04:43:48 UTC