Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Apply progressive enhacement strategy for documents #4

Open
csarven opened this issue Mar 2, 2015 · 2 comments
Open

Apply progressive enhacement strategy for documents #4

csarven opened this issue Mar 2, 2015 · 2 comments

Comments

@csarven
Copy link

csarven commented Mar 2, 2015

Information should be accessible as much as possible by lowering the barriers or requirements for both humans and machines. For example, if some information is meant to be accessible by both of those actors, it should be available from ground up, starting from HTML. A counter-approach to this is injecting the information through JavaScript e.g., http://renatostauffer.ch/bachelor-thesis/package-plan/ , which practically means that the user-agent 1) is capable of applying JavaScript 2) JavaScript is enabled. One quick test: use Lynx (or another text-based browser) to see what information is 'essentially' accessible.

[Keep this issue open until end of BT]

@reni99
Copy link
Owner

reni99 commented Mar 2, 2015

Well what I could do is to create the html-tree with the given javascript I made with google charts and then copy paste the generated html into my website. So no javascript will be needed anymore for visitors.

@csarven
Copy link
Author

csarven commented Mar 2, 2015

ol is your friend. KISS. The HTML that's coming from Google Charts is inappropriate i.e., it does not semantically represent the information.

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

No branches or pull requests

2 participants