You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 29, 2019. It is now read-only.
"Dynamic content":'yes' could be more descriptive. With dynamic content we could have search pages, single page forms, multipage forms, filters, video content, all kind of buttons with open and close, fullscreen, interactive tools, a video playing with links etc. I cant imagine a situation a tool can do all, so this category should be more specific. For example: testing of single page forms, analysing search results, speech analysis etc
The text was updated successfully, but these errors were encountered:
I think the corresponding section 2.1.4 needs better description. It is actually less "dynamic content" but rather "user emulation". So actually not the "yes" is the problem but more the "relies on browser capabilities" that does not make sense in relation to section 2.1.4. See also Issue #18
nitedog
changed the title
Section 3.4 - Additional info (Hanno Lans)
Section 3.4 and 2.1.4 - Dynamic content (Hanno Lans)
Sep 1, 2014
Reference
http://lists.w3.org/Archives/Public/public-wai-ert-tools/2014Aug/0004
Original Comment
"Dynamic content":'yes' could be more descriptive. With dynamic content we could have search pages, single page forms, multipage forms, filters, video content, all kind of buttons with open and close, fullscreen, interactive tools, a video playing with links etc. I cant imagine a situation a tool can do all, so this category should be more specific. For example: testing of single page forms, analysing search results, speech analysis etc
The text was updated successfully, but these errors were encountered: