How to stop search engines (duck duck go/google in particular) to cut titles of web pages - search-engine

Some titles of search results get cut of with three dots (...). This is very annoying, especialy when you search for coding errors, because the relevant information is at the end of the title. See example:
Is there a possibility to make Duck Duck Go or Google show the entire title of a page?
Is there an alternative search engine, which shows the entire page title?

Just try to keep your titles between 50-70 chars.
If you will make them longer, Google can crop even to 40-50 chars.

Related

LaTeX Beamer http request (Media9)

I am trying to make a survey a part of my beamer presentation. So the idea is that I have made a webpage, where one can input a number:
https://martinbytes.com/numbers/
which then saves it on the server. Then I have another webpage, which by a simple http request calculates the average of the numbers people have put in:
https://martinbytes.com/numbers/result.php
What I now want to do is to implement this into my beamer presentation. So on one slide I give them the first webpage and for instance asks them to evaluate the course on a scale 1-10, then when I change the slide I want the average to be on the slide by loading the second webpage into the presentation at the time the slide opens.
What I have tried so far is to use the media9 package, but I can not make it work. This is what I have so far:
\includemedia[
width=0.46\linewidth,height=0.2\linewidth,
activate=pageopen, deactivate=pageclose,
flashvars={
src=https://martinbytes.com/numbers/result.php
},
]{}{StrobeMediaPlayback.swf}%
But this gives me TypeError - Error#1009. How can I fix this?

Can we make VoiceOver skip the contents of a container, sometimes?

In one of our native iPad apps, there's a screen divided into a number of sections. For the most part, I think it works well with VoiceOver. But one of those sections is a UIWebView that displays web content related to the app, but provided by another vendor. It's essentially a black box to us. So I have no control over what that content is (or how accessible it is), it's incredibly dense with little nuggets of content, and it's on the left side of the screen, so it comes before a lot of the other content in (English) reading order.
As a consequence, if I ask VoiceOver to read through the contents of the screen, it quickly gets bogged down in this web content, and I can't imagine many people sticking it out to the remainder of the screen. But making them give up and scrub the screen to discover things seems obnoxious.
What I would love to be able to do would be to have the read-through treat that whole region as a single unit and use a summary label or heading, but still allow the user to point into it or toggle it somehow to allow interaction with the web content. Is there any way to accomplish this on iOS (without completely confusing the accessibility system)?
Of course, I'm sighted, so I'm also acting on speculation to some extent. Would the current UI be as confusing to users relying on VoiceOver as I think? Is what I'm describing as my solution going to be an even worse situation?
aria-hidden="true" would make a screen reader ignore the whole content (if this screen reader is modern enough to take into account WAI-ARIA. VoiceOver is).
That isn't what you're trying to achieve I guess, and most of the time it isn't desirable: why would screen reader users not able to read the same content as others, who are you to decide for them what they can/can't read that other people can't/can? Except in known cases of complete inaccessibility like a keyboard trap and this keyboard trap can't be fixed for now
a skip link before this content would allow SR users to jump to the content that is after this section.
if relevant, known ARIA landmark roles would allow to choose which part of the page they want to read (it would need this section to be the whole sidebar - complementary role - or the main one. Probably not the case)
SR can navigate through headings (as well as links and sequential reading and now landmark roles).
If this section and the next one begin with good headings, then it can be bypassed quickly.
Relevant WCAG 2.0 Techniques:
Providing heading elements at the beginning of each section of content (H69)
Providing descriptive headings (G130)
Using h1-h6 to identify headings (H42)
Organizing a page using headings (G141)
 
If there's no heading element and it can't be modified, but there's some text that could've been a relevant heading except it's a paragraph or item list or whatever, it could be marked as an equivalent with ARIA by using role="heading" and aria-level="N" (see role="heading")
if you've a good reason to modify the natural reading order of columns (I think this is the case here), you can modify layout with floats and flexible box layout (IE10+) (latter has had 3 different syntax throught the years, plugins like autoprefixer are welcome, or SASS/Compass...). Your left column would then appear last when tabbing but that requires modifying the layout of maybe a lot of templates.
aria-describedBy can probably be useful in some way but I've not enough knowledge about its uses, maybe somebody else will know more about it.
From comments Sixteen said:
Unfortunately, like I said, I don't have any control over that content at all. It comes from elsewhere, and is being displayed by our app
I agree with Felipe. I don't know what your code looks like, but say this in basic HTML. You probably either embed the code with an iframe, or inject the content into your code (example PHP include()).
Regardless on the method you use, you probably wrap a <div> around it. So you could do
<div aria-hidden="true">
//iframe/inject here
</div>
to make it not be seen by AT. Taking this basic model, we could pull out aria-hidden="true" and replace with role="complementary". You could put text in the div, push it off screen and say a nice line, and same for aria-described by, but you may want to tack on tabindex to it. Ex:
<div aria-describedby="ex" tabindex="-1">
<p id="ex" class="offscreen">Below is useless jargon by blah blah blah. It may
be more beneficial to jump to the main section instead.</p>
//iframe/inject here
</div>

footer not the same on every page

I am relatively new to coding, html etc, and have only really written two websites before this. I am a graphic designer by profession and I am attempting a website provided by a client. I am still working on it but have come across a problem I just cant fix...
The footer appears to be different on every page, It is perfect on the home page, and seems to be ok on the about (apart from the gap underneath :/) but I cant sort it out on the testimonials or the contact.
Any help would be much appreciated
The site its currently on is: http://www.eplsdesign.com/grow/index.php
Thanks
Firstly, you are using <font> and <b> tags in the HTML. Nowadays, all styles (font, color, font-weight etc.) should always be specified via CSS. This makes the HTML much cleaner and easier to maintain.
Your pages look different because each page has a slightly different structure. On the Home page, the footer div is nested at the same level as your main content div. But on the Testimonials page, the footer is actually inside content. You need to be consistent with your page structure to achieve a consistent look. Getting rid of the <font> and <b> tags will help you do this.
I'd suggest you read up on basic HTML and CSS before continuing.

Best way to link images to text so that localization keeps things spaced properly?

I've got an app with a big 'help' page that describes how to use it. This page features a lot of text with some embedded images. Is there some way to 'link' or attach these images to the bottom of specific text boxes so things will lay out reasonably well for any localization we do? In other words, if the French translation of a block of text ends up being two lines longer than the English equivalent, I'd like the image that's placed below that text to be pushed downward by the appropriate amount without having to re-edit the layout of of the .xib file manually. Possible?
You can make HTML page. You can place any thing after your text and can do modification. As it is HTML page it can easily wrap and auto adjust itself. And show the html page in your webview by saving the HTML page in your local data storage

RSS app in iOS: Detecting the existence of a feed through UIWebView

I'm making an RSS app.
In my "Add Feed" tab there is a UIWebView covering half of the page. I want to be able to google search or type in a website in my web view. On the other half of the page I want to have any feeds that are detected in the UIWebView to be displayed.
When the feeds/feed URL's are displayed, I want them to be next to a "plus" or "add" button. When clicked the feed is then added/saved to a UITableView in another tab.
I'm not asking anyone to write the code for me, but if anyone knows where to start or if there's a certain class that would help, please let me know! Or even a tutorial that gets me on the right track!
Here's an app that has the feature I'm talking about (the detection part) I just want to display it a different way. http://itunes.apple.com/us/app/free-rss-reader/id290537970?mt=8
Any Help is greatly appreciated. Thanks.
Once loading is complete, fetch the HTML content of the web view:
[webView stringByEvaluatingJavaScriptFromString:#"document.documentElement.outerHTML"];
Use a regex or some other method to parse through the content and extract the href and title attributes of the anchor tags.
Use a heuristic to look for link titles or hrefs containing "rss", "feed", or "xml", which may indicate an RSS link.
Present the filtered list of links to your user.

Resources