Skip to content
This repository has been archived by the owner on Jan 29, 2019. It is now read-only.

Section 3.4 and 2.1.4 - Dynamic content (Hanno Lans) #40

Closed
darthcav opened this issue Aug 20, 2014 · 2 comments
Closed

Section 3.4 and 2.1.4 - Dynamic content (Hanno Lans) #40

darthcav opened this issue Aug 20, 2014 · 2 comments

Comments

@darthcav
Copy link

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

@nitedog nitedog changed the title Section 3.4 (Hanno Lans): Additional info Section 3.4 - Additional info (Hanno Lans) Sep 1, 2014
@nitedog
Copy link
Contributor

nitedog commented Sep 1, 2014

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 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
@darthcav
Copy link
Author

Resolution

Accept. See issue #18.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants