) basically shares the goal of the amendment, but points out that the complete accessibility of public transport is only a political goal. Accessibility, according to the position of the BAG, remains “a process of approaching an ideal and a compromise between the needs of different groups of people”. A barrier-free public transport system “offers more comfort and accessibility for all passengers, regardless of special needs, temporary or permanent disabilities”, says Dirk Bräuer, head of an ad hoc working group of the Federal Working Group for Public Transport of the municipal umbrella organisations and responsible in Chemnitz for service planning and local transport plans. However, freedom from obstacles for all forms of disability is “realistically not achievable”. Since the PBeFG did not formulate any technical or content requirements, the definition of local standards for accessibility is incumbent on “the responsible bodies in coordination with transport companies, building authorities and associations, representatives and advisory boards of the affected persons on the basis of the generally recognised rules of technology”.
According to § 4 PBeFG “structural and other facilities, means of transport (…)” are barrier-free “if they are accessible and usable for disabled persons in the generally customary manner, without particular difficulty and basically without outside help”. In order to achieve barrier-free accessibility, there must first be sufficient usable transport connections available which can also be reached by those affected. On the traffic routes themselves, i.e. on paths and road crossings, there must be evenness and unity. Contrasts and the comprehensibility of information according to the two-sense principle, for example through display boards and loudspeaker announcements, serve as necessary orientation.
“Barrier-free traffic facilities are to be declared a standard for new buildings and conversions,” says the FGSV, pointing out that according to the PBeFG, the approval of a transport service can be prohibited “if it is not in line with the local transport plan in terms of barrier-free access”. In order to achieve accessibility in public transport, the research community proposes a departure from the previous “sectoral planning approach” to a “holistic one based on an analysis of the needs and wishes of all passengers and on the involvement of users at every stage of the development process”.
Even if the PBeFG itself does not contain any comments on this, the planning of barrier-free public transport facilities is likely to be based on already existing technical standards. An example of this is DIN 18040-3 for public transport stops and track systems. According to this standard, stops must be easy to find and accessible. Stops and means of transport must be coordinated in such a way that barrier-free use is possible. At transfer points, chains of routes between means of transport should be created, supported by orientation and guidance systems. The standard also recommends equipping stops with weather protection. Stop shelters, platforms and bus shelters can only be used without barriers if there are seats available.
Five years after the amended PBeFG came into effect, the expert Johannes Wolf draws a differentiated conclusion in the renowned trade journal Straßenverkehrstechnik (SVT 4-2016): “exemplary results” have been achieved especially in the field of trams and in large cities. However, the mass of bus stops available in the public road network showed that there was a considerable need to catch up on what had been achieved with trams. This was “not only due to a series of legislative inconsistencies, wrong decisions and a chain of omissions, but also to a lack of initiative on the ground” and not least “also due to a difficult financial situation”.
Accessible stops help to improve mobility for all, but they must also be accessible and served. And this requires a sufficient range of transport services. However, this is declining in many rural regions due to declining numbers of schoolchildren. Citizens’ buses, call and collective taxis and “other demand-oriented or flexible forms of service that supplement regular transport outside rush hours or bridge the distance between the front door and the bus stop” could, according to one affected person, close the gaps. However, existing transport models should not be weakened by decisions of the transport companies. This refers to decisions to exclude e-scooters from transport in local buses (KOMMUNAL of 19.03.2015, article “Unterwegs mit einem Wheelchairfahrer”).
In conclusion: Whether complete accessibility in public transport will actually be achieved by 2022 or ever thereafter seems rather questionable in view of the complex requirements and the limited financial means of the public transport authorities. Realists speak not without reason of approaching an ideal. For the legislator’s wish to have any prospect of realisation in town and country, it requires not only the will and commitment of those involved but also the necessary financial resources. And last but not least a sufficient offer of transport.<issue_start><issue_comment>Title: TypeError: e.join is not a function
username_0: **Describe the bug**

**To Reproduce**

**Expected behavior**

**Screenshots**

**Applicable Versions:**
 - Netlify CMS version: `netlify-cms-app@2.12.16`
 - Git provider: `github`
 - Browser version: `Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36`

**CMS configuration**
```
publish_mode: simple
slug:
  encoding: unicode
  clean_accents: false
  sanitize_replacement: "-"
backend:
  name: github
  repo: abogutalan/i3-website
  commit_messages:
    create: Create {{collection}} “{{slug}}”
    update: Update {{collection}} “{{slug}}”
    delete: Delete {{collection}} “{{slug}}”
    uploadMedia: "[skip ci] Upload “{{path}}”"
    deleteMedia: "[skip ci] Delete “{{path}}”"
media_folder: static/myAssets/img/
public_folder: /myAssets/img
collections:
  - view_filters: []
    meta: {}
    name: instructors
    slug: "{{name}}-{{templateKey}}"
    folder: src/pages/YD/YDInstructors
    publish: true
    sortableFields:
      - commit_date
      - name
      - name
      - description
    label: Instructors
    fields:
      - label: Template Key
        name: templateKey
        widget: hidden
        default: instructorTemplate
      - name: name
        label: Instructor Name
        widget: string
      - name: imgURL
        label: Featured Image
        widget: image
      - name: description
        label: Description
        widget: text
      - name: descriptionMore
        label: More Description
        widget: text
        required: false
    create: true
  - view_filters: []
    meta: {}
    name: locations
    slug: "{{name}}-{{templateKey}}"
    folder: src/pages/YD/YDLocations
    publish: true
    sortableFields:
      - commit_date
      - name
      - name
    label: Locations
    fields:
      - label: Template Key
        name: templateKey
        widget: hidden
        default: locationTemplate
      - name: address
[Truncated]
      - name: linkedin_url
        label: LinkedIn URL
        widget: string
        default: ""
        required: false
    create: true
  - view_filters: []
    meta: {}
    name: event
    slug: "{{name}}-{{templateKey}}"
    folder: src/pages/programs/Events
    publish: true
    sortableFields:
      - commit_date
      - name
      - name
      - description
    label: Events
  
...
<issue_comment>username_1: Hi @username_0 can you provide some more context on the source of the error?
Please attach a screenshot/repo link if possible.
<issue_comment>username_1: Closing due to missing information<issue_closed><gh_stars>1000+
/**
 * @license
 * Copyright Google LLC All Rights Reserved.
 *
 * Use of this source code is governed by an MIT-style license that can be
 * found in the LICENSE file at https://angular.io/license
 */

import {ifEnvSupports} from '../test-util';
declare const global: any;

describe('FileReader', ifEnvSupports('FileReader', function() {
           let fileReader: FileReader;
           let blob: Blob;
           const data = 'Hello, World!';
           const testZone = Zone.current.fork({name: 'TestZone'});

           // Android 4.3's native browser doesn't implement add/RemoveEventListener for FileReader
           function supportsEventTargetFns() {
             return!!FileReader.prototype.addEventListener &&
                !!FileReader.prototype.removeEventListener;
           }
           (<any>supportsEventTargetFns).message =
               'FileReader#addEventListener and FileReader#removeEventListener';

           beforeEach(function