Go to file
Cameron Cundiff 9a74c7b99b Do not generate default alt text in image tags
- Auto-generating content from the filename of an image is not suitable
  alternative text; alt text that isn't fully considered can be
  distracting and fatiguing for screen readers users (blind, low vision,
  dyslexic people).
- Setting a filename fallback short circuits screen reader default
  behavior and configuration for blank descriptions.
- Setting poor defaults also creates false negatives for accessibility
  linting and testing software, that makes it harder to improve
  application accessibility.

***

- After this change, if authors leave images without alt text, screen
  readers will fallback to default behavior for missing alt text.
- Also with this change, Automated linting and testing tools will
  correctly generate warnings.

[Fixes #30096]
2017-08-17 16:13:15 -04:00
.github Limit stale checks to issues 2017-04-01 11:27:26 -05:00
actioncable Fix RuboCop offenses 2017-08-16 17:55:25 +09:00
actionmailer Do not generate default alt text in image tags 2017-08-17 16:13:15 -04:00
actionpack Fix RuboCop offenses 2017-08-16 17:55:25 +09:00
actionview Do not generate default alt text in image tags 2017-08-17 16:13:15 -04:00
activejob Wait for the Delayed Job worker thread to finish 2017-08-13 22:03:40 +09:30
activemodel [ci skip] Postgres --> PostgreSQL 2017-08-08 18:20:44 +09:00
activerecord Add space 2017-08-16 12:55:29 -04:00
activestorage Do not generate default alt text in image tags 2017-08-17 16:13:15 -04:00
activesupport Fix RuboCop offenses 2017-08-16 17:55:25 +09:00
ci Use frozen string literal in ci/ 2017-08-13 22:07:54 +09:00
guides Do not generate default alt text in image tags 2017-08-17 16:13:15 -04:00
railties Fix RuboCop offenses 2017-08-16 17:55:25 +09:00
tasks Use frozen string literal in tasks/ 2017-08-13 22:04:42 +09:00
tools Use frozen string literal in tools/ 2017-08-13 22:04:59 +09:00
.codeclimate.yml Generators and tests are under the same style rules 2016-07-27 20:26:39 -03:00
.gitattributes adds .gitattributes to enable Ruby-awareness 2016-03-16 11:15:22 +01:00
.gitignore Test rails-ujs in our travis matrix 2017-02-22 13:49:28 -05:00
.rubocop.yml Fix RuboCop offenses 2017-08-16 17:55:25 +09:00
.travis.yml Run Active Storage service tests in CI 2017-08-14 13:48:17 -04:00
.yardopts Let YARD document the railties gem 2010-09-09 18:24:34 -07:00
CODE_OF_CONDUCT.md Move the CoC text to the Rails website 2015-08-21 12:32:59 -07:00
CONTRIBUTING.md Remove html tag making markdown misrender [ci skip] 2017-06-05 22:11:57 -05:00
Gemfile Test with released thor 2017-08-16 14:03:24 -04:00
Gemfile.lock Test with released thor 2017-08-16 14:03:24 -04:00
MIT-LICENSE Bump license years for 2017 2016-12-31 08:34:08 -05:00
RAILS_VERSION Start Rails 5.2 development 2017-03-22 10:11:39 +10:30
README.md Add Active Storage to README and release (#30065) 2017-08-04 17:55:24 -05:00
RELEASING_RAILS.md Update release instructions in light of new tasks. 2017-07-22 21:17:44 +02:00
Rakefile Use frozen string literal in root files 2017-08-13 22:14:24 +09:00
rails.gemspec Use frozen string literal in root files 2017-08-13 22:14:24 +09:00
version.rb Use frozen string literal in root files 2017-08-13 22:14:24 +09:00

README.md

Welcome to Rails

Rails is a web-application framework that includes everything needed to create database-backed web applications according to the Model-View-Controller (MVC) pattern.

Understanding the MVC pattern is key to understanding Rails. MVC divides your application into three layers, each with a specific responsibility.

The Model layer represents your domain model (such as Account, Product, Person, Post, etc.) and encapsulates the business logic that is specific to your application. In Rails, database-backed model classes are derived from ActiveRecord::Base. Active Record allows you to present the data from database rows as objects and embellish these data objects with business logic methods. You can read more about Active Record in its README. Although most Rails models are backed by a database, models can also be ordinary Ruby classes, or Ruby classes that implement a set of interfaces as provided by the Active Model module. You can read more about Active Model in its README.

The Controller layer is responsible for handling incoming HTTP requests and providing a suitable response. Usually this means returning HTML, but Rails controllers can also generate XML, JSON, PDFs, mobile-specific views, and more. Controllers load and manipulate models, and render view templates in order to generate the appropriate HTTP response. In Rails, incoming requests are routed by Action Dispatch to an appropriate controller, and controller classes are derived from ActionController::Base. Action Dispatch and Action Controller are bundled together in Action Pack. You can read more about Action Pack in its README.

The View layer is composed of "templates" that are responsible for providing appropriate representations of your application's resources. Templates can come in a variety of formats, but most view templates are HTML with embedded Ruby code (ERB files). Views are typically rendered to generate a controller response, or to generate the body of an email. In Rails, View generation is handled by Action View. You can read more about Action View in its README.

Active Record, Active Model, Action Pack, and Action View can each be used independently outside Rails. In addition to that, Rails also comes with Action Mailer (README), a library to generate and send emails; Active Job (README), a framework for declaring jobs and making them run on a variety of queueing backends; Action Cable (README), a framework to integrate WebSockets with a Rails application; Active Storage (README), a library to attach cloud and local files to Rails applications; and Active Support (README), a collection of utility classes and standard library extensions that are useful for Rails, and may also be used independently outside Rails.

Getting Started

  1. Install Rails at the command prompt if you haven't yet:

     $ gem install rails
    
  2. At the command prompt, create a new Rails application:

     $ rails new myapp
    

    where "myapp" is the application name.

  3. Change directory to myapp and start the web server:

     $ cd myapp
     $ rails server
    

    Run with --help or -h for options.

  4. Using a browser, go to http://localhost:3000 and you'll see: "Yay! Youre on Rails!"

  5. Follow the guidelines to start developing your application. You may find the following resources handy:

Contributing

Code Triage Badge

We encourage you to contribute to Ruby on Rails! Please check out the Contributing to Ruby on Rails guide for guidelines about how to proceed. Join us!

Trying to report a possible security vulnerability in Rails? Please check out our security policy for guidelines about how to proceed.

Everyone interacting in Rails and its sub-projects' codebases, issue trackers, chat rooms, and mailing lists is expected to follow the Rails code of conduct.

Code Status

Build Status

License

Ruby on Rails is released under the MIT License.