Accessibility Auditor Recent Data Not Available Feature Missing

System & Server Adminstration
1

Hi all,

We’ve enabled the Accessibility Auditor for a web collection via the colleciton.cfg setting,

accessibility-auditor.check=true

After a few successful crawls, we’re seeing this error in the marketing dashboard,

image.png654×1040 64.8 KB

An error message I can spot regarding data being missing / not accessible, is a modern UI error which popped up close to crawl,

/opt/funnelback/log/public-ui.warnings
Fri Sep 22 16:16:57 2017 - Could not open collection cache file /opt/funnelback/lib/perl/Funnelback/../../../cache/demo-puc-search-collection.cfg.cache: Permission denied
Fri Sep 22 16:21:57 2017 - Could not open collection cache file /opt/funnelback/lib/perl/Funnelback/../../../cache/demo-puc-search-collection.cfg.cache: Permission denied

There also looks to be accessibility filter issues re PDFs in the crawler inline filter log,
2017-09-22 19:04:24,782 [com.funnelback.crawler.NetCrawler 6] WARN delegatetechnique.ErrorIgnoringTechnique - Error when checking for PDF6 on http://www.puc.edu/__data/assets/pdf_file/0020/144263/Catalog-2016-2018.pdf?v=0.1.6
java.lang.NullPointerException
at com.funnelback.accessibility.pdf.utils.RecursingCOSVisitor.traverseObject(RecursingCOSVisitor.java:180) ~[funnelback-wca-checker.jar:?]
at com.funnelback.accessibility.pdf.utils.RecursingCOSVisitor.visitFromDictionary(RecursingCOSVisitor.java:121) ~[funnelback-wca-checker.jar:?]
at org.apache.pdfbox.cos.COSDictionary.accept(COSDictionary.java:1451) ~[pdfbox-1.8.10.jar:1.8.10]
at com.funnelback.accessibility.pdf.utils.RecursingCOSVisitor.traverseObject(RecursingCOSVisitor.java:180) ~[funnelback-wca-checker.jar:?]
at com.funnelback.accessibility.pdf.utils.RecursingCOSVisitor.visitFromDocument(RecursingCOSVisitor.java:150) ~[funnelback-wca-checker.jar:?]
at org.apache.pdfbox.cos.COSDocument.accept(COSDocument.java:578) ~[pdfbox-1.8.10.jar:1.8.10]

Neither should be preventing any analytics data from coming back though.

2

Hi Tim,

What version are you running. And are you able to click on the Accessibility Auditor link in the LH menu?

There was a bug reported (since fixed) a while back which caused the no data available tile to be displayed, but the LH link still worked.

cheers,
Peter

3

If that’s not working it might also be worth visiting http://server/s/accessibility-auditor.json?collection=COLLECTION to see if any error is returned

4

Hey Pete!

Running 15.10.0, on the Squiz US Demo Server.

Turns out I can click on the link in the Accessibility Auditor LH menu and bypass that error. But when I click through, I see:

Strangely enough, heading to the accessibility-auditor.json URL, results in a redirect to 127.0.0.1, so it could be related to the fact that we haven’t enabled an SSL certificate on the server yet,

https://squizus-demo-funnelback01.sac1.squiz.systems/s/accessibility-auditor.json?collection=demo-puc-search/s/accessibility-auditor.json?collection=demo-puc-search

https://127.0.0.1:8443/s/accessibility-auditor.json?collection=demo-puc-search/s/accessibility-auditor.json?collection=demo-puc-search

5

Hi @ttran -

You’re pretty close to the mark there in your analysis. Loading the report in the marketing dashboard and viewing your browser console should reveal which requests to JSON endpoints are going unmet.

Certain combinations of web server / OpenResty configurations deployed on top of Funnelback might need to be altered to allow requests to the /s/accessibility-auditor.json endpoint to be opened up in v15.10+. You may need to add a section like the following:

#/etc/openresty/conf.d/funnelback.conf
...
server {
....
location /s/accessibility-auditor.json {
    proxy_pass      https://https-admin;
}
....

Restart OpenResty, and you’ll be away.