Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 days ago.
Improve this question
What is the best way to check a website's WCAG 2.1 accessibility standard? I want to generate a report if a website's accessibility is of a AA WCAG 2.1 standard.
Producing such report is called an accessibility audit.
For the way to check, the Website Accessibility Conformance Evaluation Methodology (WCAG-EM) 1.0 is the relevant standard, which is part of the WCAG 2.
It describes how to proceed in an audit:
Define the Evaluation Scope
Explore the Target Website
Select a Representative Sample
Audit the Selected Sample
Report the Evaluation Findings
Further, there is guidance on involving users and using evaluation tools, both of which are optional for conformance with the EM.
For most people, it’s impossible to evaluate all success criteria without using a tool.
There a plenty of spreadsheet solutions out there that help with the evaluation, some governments providing spreadsheets based on their national adoption of the WCAG.
The Web Accessibility Initiative created their own, simple WCAG-EM Report Tool, and then there are several commercial solutions.
In my opinion, the following criteria matter:
Combine automatic and manual testing
Only a smaller part of a site’s performance can be checked automatically, so you’d need a tool that guides you through the manual parts as well.
Ideally, the automatic parts would already be covered and taken into account.
Avoid re-evaluation of common components
Modern sites, especially web applications, are constructed component-based, with components re-appearing on each page. These are based on the exact same code and will behave the same across pages. Like header, navigation and footer.
A page-based evaluation is therefore not very practical.
An ideal tool™ would take into account that these exist and re-use the component’s evaluation for each page that includes the component.
Tools that provide these features
The market leader on accessibility tools is deque with their axe suite. They offer the axe Auditor, which starts evaluation of each page with an automatic audit, and then guides the auditor through the remaining manual checks, providing a combined report at the end.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 5 years ago.
Improve this question
For a beginner hobbyist, it seems fairly common to create everything in the order it will be viewed by the user, regardless of its importance, and to intertwine back-end and front-end development.
Obviously, this isn't the most efficient method and would probably be avoided by more experienced developers. I've been exploring different ways to order software development, but I'd like to know if there's a standard that's widely accepted or recommended by the industry.
That is what software development processes are for.
Thing is: there are many different processes; thus there are many different answers to your question.
In 2017, most organisations use processes around the "agile" mindset (or they try to get there), thus your first stop could be Agile software development.
And to give a direct answer to your question:
when you start an agile project, you simply don't know about "all the things the user will view"
instead, you collect requirements
you translate requirements into "user stories"
then the development team and the users (or user representatives) decide on the priority of those user stories
and then, during the development iterations (sprints) a subset of the "most important" user stories is implemented
The key part here: requirements and their priorities are subject to change. The idea to collect everything upfront, to then define an order over all items is simply rejected nowadays.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
I am writing a research on a service ranking algorithm, and I want to prove its performance and accuracy by running it on a public data. let's say apple store data, google play, expedia etc. Can I parse their data from HTML and use it in my research? or I would be performing illegal act (web scraping)?
And should i mention explicitly in my research that the data is used only for scientific reasons?
I've read about webscraping and the controversies about its illegality, but i did not find any article about if it's used for scientific purposes only.
Thanks in advance
There is nothing inherently illegal about web-scraping a site.
However, I would suggest that you pay attention to the particular site's "Terms of Use" to see if it is something which they expressly forbid. For example, the Expedia Terms of Use here http://www.expedia.ie/p/support/termsofuse outline:
you may not visit or make available the website or any part of the web
pages of the website by automatic means, such as by using crawlers or
shop bots to systematically retrieve or copy information or connect
the content of the website functionally to another website via links
*That being said, as long as you don't exert an unreasonable load on the site, or republish their content as your own, I don't expect you will run into any problems.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I am going to develop a journal system which has paper submission and review actions with evalution forms,something like OJS system. I want to use drupal for it but I am not sure if it is a good choice.
Does Drupal have ability to create such applications ?
It is a very generic question. To answer some part:
Drupal can be customized and used for a lot of projects, thanks to the powerful community and module developers.
Let me give a glimpse of possibilities, you can find the rest:
Each paper can be a content type. Each user can have specific roles and permissions (eg. publisher, editor, reviewer etc) who are allowed to do specifically what you allow them to do. They can apply for higher roles as well.
Each review process can be captured and maintained using workflow module. There are plenty of tutorials for that.
List of articles can be shown with various properties and filters using views. They can be shown in various regions of a theme you select or make of your own (or customize).
The community can be built using forums.
In short there are thousands of possible ways you can make this. But one note from personal experience: sometimes you will find extremely tough things to be done in simple ways, while simple things will take time. This is mostly because like all systems, it takes a bit of time to get used to with the drupal api.
Best of luck!
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
We're after a replacement for a DotNetNuke installation with a DynamicForms module by DataSprings.
Currently the problems are mainly performance related, but the fact that DynamicForms uses Postbacks on ASP.Net all the time renders it also highly susceptible to slow server response time.
We're after a Drupal module which would allow us to present the CMS user with a control panel where they could:
- create new surveys
- assign a target group for the surveys
- manage the questions:
- checkbox/radiobutton/combobox/open questions
- variations of the above - e.g. a combobox with a text field when "other" was chosen
- the support for data lists, e.g. "what state do you live in" with values stored in the database and managed separately.
- conditional questions (show/hide) further questions when a certain option is chosen
- grouping questions (hiding sets of questions at a time)
- scrapbook function (storing frequent questions and being able to easily copy them into the new poll)
- exporting the poll data along with selected attributes from the user profile
As you can see the requirements are huge, and we're looking for an Open Source alternative to the current solution, which would allow us to extend the module if necessary.
Drupal would be the platform of choice, but we're flexible in that respect.
I'd appreciate your suggestions of alternatives.
There is a similar discussion going on at Drupal.org. IMHO, Drupal just isn't perfect for complex surveys. Limesurvey is much better when it comes to different types of questions, conditional blocks, reusable question types etc. However in Limesurvey 1, the admin interface is awkward and theming/templating system is not great. Limesurvey 2 looks very promising, but it's in beta.
Your best choice should be a new drupal module integrating the LimeSurvey software :
http://drupal.org/project/limesurvey_sync
Have a look at Webform
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
How many people actually write an SDD document before writing a single line of code?
How do you handle large CSCI's?
What standard do you use for SDD content?
What tailoring have you done?
I certainly have. Historically and on recent projects.
Years ago I worked in organisations where templates were everything.
Then I worked other places where the templates were looser or non-existent or didn't fit the projects I was working on.
Now the content of the software design is pretty much governed by what I need to describe to get the idea across to the audience.
"before writing a single line of code" there wouldn't be a a lot of detail. The documents I produce before I start coding are meant to get the idea of what we need to build across to the affected teams and senior management so they introduce high level architecture, functionality, technologies, risks and scope. Those last two are really important. The rest is to show other teams where you need to interface with them and to leave managers with a lingering notion that cool stuff is happening.
Most big software companies have their own practices. For example Motorola has detailed documentation for every aspect of software development process. There are standard templates for each type of documents. Having strict standards allows effectively maintain huge number of documents and integrate it with different tools. Each document obtains tracking number from special document-tracking system. They even have system (last time I seen it was in stage of early development) for automatically requirements tracking - you can say which line of code relate to given requirement\design guideline.
I would suppose that most people who write SDD documents and use terminology like CSCI have to be using a specific software development methodology and most likely are working for some serious government customer. They usually tend to take their preparations quite seriously and the documents are ready and approved before any development starts.
In an Agile process the development and the design document could be developed in parallel. It means that there will be plenty of refactoring to be done but it usually delivers very good results in the end.
In more formal processes (like RUP) a SAD document is mostly created during the elaboration/prototyping phase based on the team research.