I'm trying to debug a Kindle ebook that has both footnotes and internal navigation, on a Kindle e-ink reader. The problem is, some of the links that should take you to a different page are instead interpreted as footnotes showing up in a popup at the bottom of the page.
How does the Kindle decide whether a link is for navigation or is a footnote? There's no attribute on the HTML <a> tags that would indicate each behavior.
According to the Kindle publishing guidelines,
To avoid unintended footnote pop-ups, internal links that are not
footnotes should not be formatted with bidirectional hyperlinks (A
links to B and B links to A) Non-footnote links should use the format
A links to B and B links to C instead.
Related
I have an application in which one of the modules consists of a UIWebView in which articles are shown as HTML pages.
The problem is the articles could contain basically any outside link to images, videos other articles (from other providers), even adult content. In short it can contain links to unmoderated content.
Is it safe to open these links in the the applications UIWebView or are there some rules on what can be loaded in an applications? Should I just not open those links in the application and just open it with safari?
I am going to take Microsoft 70-486 (MVC) exam. So i am preparing for it. Came across one most important question asking in 70-486 exam but the answer is different across web, Please help to choose the correct answer.
Question
You are designing an HTML5 website. You need to design the interface to make the content of the web page viewable in all types of browsers, including voice recognition software, screen readers, and reading pens. What should you do?
Annotate HTML5 content elements with Accessible Rich Internet
Application (ARIA) attributes.
Convert HTML5 forms to XForms.
Ensure that HTML5 content elements
have valid and descriptive names.
Use HTML5 semantic markup elements
to enhance the pages.
Use Resource Description Framework (RDF) to
describe content elements throughout the entire page.
In some website it is mentioned as AD is correct answer check this enter link description here and others mentioned ABCD is correct answer check this enter link description here. I am confused between this 2 ans.
I would say that the correct answers are :
Annotate HTML5 content elements with Accessible Rich Internet Application (ARIA) attributes : It is the primary role of the aria attributes !
Use HTML5 semantic markup elements to enhance the pages : To help the screen readers to know that an element is a nav, an article...
Ensure that HTML5 content elements have valid and descriptive names : i.e. to help the screen readers to know that an input is the "FirstName", and not just a "Text input", a better approach is to use a label for the inputs, but after reading this article, it seems that only few screen readers manage the label element.
I'm gonna correct Djoul6's answer a bit.
Ensure that HTML5 content elements have valid and descriptive names.
This is not a correct answer. the name attribute can be whatever, screen readers do not read the name attribute out loud. From the source Djoul6 refered to there was this description. http://www.w3.org/TR/UNDERSTANDING-WCAG20/ensure-compat-rsv.html#namedef
name
text by which software can identify a component within Web
content to the user
Note 1: The name may be hidden and only exposed by
assistive technology, whereas a label is presented to all users. In
many (but not all) cases, the label and the name are the same.
Note 2: This is unrelated to the name attribute in HTML.
The correct answer should be
Annotate HTML5 content elements with Accessible Rich Internet Application (ARIA) attributes.
Use HTML5 semantic markup elements to enhance the pages.
So, correct answers:
Annotate HTML5 content elements with Accessible Rich Internet
Application (ARIA) attributes.
Use Resource Description Framework (RDF) to describe content elements
throughout the entire page.
Please note that the correct answer should be a complete solution for Accessible web application. HTML5 semantic markup cannot be complete solution, this only enhance the pages, also XForms cannot, and even not valid and descriptive names..
I think no question about ARIA attributes, but you can read about RDF - https://www.w3.org/TR/wai-aria/roles
For futher investigation please reffer W3C WAI-ARIA.
My understanding of HTML5 is that its semantic markup is meant to make it readable across browsers and readers. That would point to the 4th answer.
I used EpiServer CMS. I'm just wondering if n2cms has any attribute to collect links. (like LinkItemCollection in EpiServer). If not, Please give me an idea to implement.
Reference: http://sdk.episerver.com/library/cms6/Developers%20Guide/Core%20Features/Properties/How%20To/Use%20Link%20Collection%20property.htm
Thanks.
You could do this with the ContentList part and creating a bunch of redirect pages. This is best if you want to re-use the collection of links again and again.
Create a dummy placeholder page somewhere, and make it invisible.
Under that placeholder page, create a Redirect page for each link.
Where you want the collection of links to appear, drag & drop a ContentList and point the root at the dummy placeholder page. You can then write a custom HTML template to display the link however you like.
One other idea would be to use N2CMS Selection part, which gives you a checkbox list of all the pages in your site. You simply check the ones you want to list, and Selection will format a list of all the pages you checked.
With both of these methods, if you link to other pages in your site, N2 will offer to update links for you if you rename any of the target pages (as long as they're in the same N2 site).
All of this is documented in the N2CMS documentation here: https://n2cmsdocs.atlassian.net/wiki/display/N2CMS/Linking+to+Content?src=search
Look under the heading Dynamically Linking to Content Items
If you search for "richfaces" in google.com, the first result will be about www.jboss.org/richfaces. You may watch there that links (menus) like "Downloads", "Demos", "Documentations" are also displayed. How to have these links displayed in the search results?
(The "description" meta tag not enough I hope)
You are not able to make Google show links to your site (they will do this if they deem your site is relevant enough to warrant providing this feature). However, you can remove these links if they are present, if they are inappropriate.
See http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=47334 for more details.
These are called Google Site Links. Google is pretty tight-lipped about how this feature is automated, but there are a handful of HTML5 tags which are supposed to help make search engines smarter. You can read more about them at O'Reilly's Dive Into HTML5 website. Especially interesting are the "Google Rich Snippets", though they're not exactly what you're looking for.
It might help to put those links in the HTML5 nav tags, like
<nav>Home About FAQ</nav>
and I've heard it tossed around that the site navigation should be an unordered list, but I don't know how true that is. Still, it couldn't hurt to do it that way and style the list with CSS.
I would show IE6 visitors a site with limited css (Progressive Enhancement) but would also like them to gently show a header informing them they can/should upgrade to a modern browser. There are initiatives out there, like ie6nomore, who do just that. But the list of modern browsers and the headertext is hardcoded.
My site is localised, so I rather have a link to an external website, that autodetects their browser language, and informs them of modern browsers in their own langauge.
That way my 'advice' will always be up to date and fully localized.
It's not a complete list, but Microsoft had to setup a browser choise page which shows the top 12 browsers, based on market share. This list will be re-evaluated every six months.
You can read more about this here:
Browser Choice FAQ
So if you detect an old browser, you could display a nice message and a link to this page.
Hope that helps.
At least safari goes directly to the windows download, so its not really a universal solution.
And its only in english.
The browser landingpages are available in all languages, so so should be the browserchoice page. Unlike firefox and chrome apple doesn't have an auto browser language detecting landingpage, so I rerouted it via google search to achieve that.
(why can't I add this as a comment to the previous post?)